From: Richard M. Stallman Date: Sun, 17 Dec 2006 22:23:07 +0000 (+0000) Subject: (Named Features): Explain subfeatures better. X-Git-Tag: archive/raspbian/1%29.2+1-2+rpi1~1^2~3372 X-Git-Url: https://dgit.raspbian.org/%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:///%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:/?a=commitdiff_plain;h=1117d6fff5781891effe221efc7090b674e7f111;p=emacs.git (Named Features): Explain subfeatures better. --- diff --git a/lispref/loading.texi b/lispref/loading.texi index eb576f8fbbc..150e20275b1 100644 --- a/lispref/loading.texi +++ b/lispref/loading.texi @@ -726,8 +726,14 @@ The argument @var{feature} must be a symbol. @code{provide} returns @var{feature}. If provided, @var{subfeatures} should be a list of symbols indicating -a set of specific subfeatures provided by this version of @var{feature}. -You can test the presence of a subfeature using @code{featurep}. +a set of specific subfeatures provided by this version of +@var{feature}. You can test the presence of a subfeature using +@code{featurep}. The idea of subfeatures is that you use them when a +package (which is one @var{feature}) is complex enough to make it +useful to give names to various parts or functionalities of the +package, which might or might not be loaded, or might or might not be +present in a given version. @xref{Network Feature Testing}, for +an example. @smallexample features